<version> <version name="foo" definedBy=".."/> <version name="bar" definedBy=".."/> // may not overlap with foo </version>
RHQ needs a more modular plugin descriptor with conditional element activation to keep up with the growing management model from AS7+ (and of course dynamic metadata).
Reasons are:
newer eap versions may/will have different/more attributes.
Layered products may have different versions of a resource type
multiplication of resource types for standalone, domain-conf, domain-rt, managed-server-conf, managed-server-rt
hide configuration resources on a HC, but show them on the DC
some elements/types are only available if a certain field is set
Plugin descriptor would get some thing like a version definition:
<version> <version name="foo" definedBy=".."/> <version name="bar" definedBy=".."/> // may not overlap with foo </version>
Expressions for 'definedBy' need to be resolved by java code for the concrete resources e.g. by looking at the version field of the Resource.class of the concrete resource. This may also need to have some fallbacks. Best is probably to add a facet/extend the standard resource component / discovery component to provide for a callback that the PC can use to determine the version with a default implementation of returning just the value of the version field. On the server side something similar is needed. Perhaps it may make sense to pre populate the children with the value from the top-most resource.
And then this version can be used in the descriptor like this.
<metric version="foo" ...> <configuration> <simple-property version="bar"
Server and agent need to
server side to show/hide UI fields
agent to only try to write existing fields (there may be a flag in as7 to ignore those writes)
Unfortunately the above is not yet enough for dependent elements / types that are only present when a certain other value is set (imagine a type of "imap configuration", that should only be shown if on a different field the type is set to 'imap'.
Another way to deal with this could be to have a "applies to parent" attribute
<service name="Foo"> <runs-inside> <parent-resource-type name="A"/> <parent-resource-type name="B"/> </runs-inside> <resource-configuration> <c:simple-property name="Bar" parent="A"/> <c:simple-property name="Baz"/>\\ <metric name="lala" parent="B"/>
Here property 'Bar' would only be present on a parent type of A, while property Baz would be available inside both parent A and B. Similar, the metric lala would be only available inside parent B
as8 will bring role based security and authorization on crudo for resources ( and perhaps even their attributes )
As8 will / should send / accept headers that define the resource version (e.g. on subsystem and server level). Our ResourceTypes may need the version information on that level and not just on the base server level. Needs to be checked with the AS team and synchronized with the console.